Skip to content

AX-2134: unify release trigger on version-file diff - #56

Merged
YoniMelki merged 5 commits into
mainfrom
feature/AX-2134-unified-release-mechanism
Sep 7, 2026
Merged

YoniMelki merged 5 commits into
mainfrom
feature/AX-2134-unified-release-mechanism

Conversation

@YoniMelki

@YoniMelki YoniMelki commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Switch release.yml from commit-subject markers to comparing plugin/.claude-plugin/plugin.json (cross-checked with marketplace.json) against the latest strict vX.Y.Z tag.
  • Merge current main and bump 1.0.23 → 1.0.24 in both manifests so merge is a real release.
  • Keep PR-time X.Y.Z validation in validate-version.yml.

Part of AX-2134.

Landing

Merging cuts v1.0.24. After that, every merge to main must bump both manifests or Release fails by design.

Test plan

  • Confirm merge creates GitHub Release v1.0.24 with release.zip.
  • Confirm both manifests agree at PR-time and release-time.
  • Confirm a follow-up merge without a bump fails with “already released”.

@YoniMelki
YoniMelki requested a review from a team as a code owner August 20, 2026 14:42
YoniMelki and others added 2 commits August 22, 2026 17:32
Co-authored-by: Cursor <cursoragent@cursor.com>
Keeps the version-file release trigger from this branch: the Release workflow
compares the manifest version against the latest vX.Y.Z tag instead of parsing
a marker out of the merge commit subject.

The only conflicts were the version line in both manifests. main had advanced
to 1.0.23, which is already tagged, so both manifests are set to 1.0.24 - the
next unused patch - so merging this PR publishes a clean release.

Co-authored-by: Cursor <cursoragent@cursor.com>
@YoniMelki
YoniMelki force-pushed the feature/AX-2134-unified-release-mechanism branch from 561a9a9 to a574f54 Compare September 3, 2026 08:52
davida-jfrog
davida-jfrog previously approved these changes Sep 3, 2026
Both sides bumped the plugin manifests from 1.0.23 to 1.0.24
independently, so the merge was textually clean but semantically wrong:
v1.0.24 is already tagged and released from main. Move the branch to
1.0.25 in plugin.json and marketplace.json so the release gate sees a
clean forward bump instead of an already-released version.

Takes main's skills sync and README version removal as-is, and keeps the
branch's release workflow, including the canonical latest-tag lookup and
the explicit partial-release rollback step.

Co-authored-by: Cursor <cursoragent@cursor.com>
@YoniMelki
YoniMelki force-pushed the feature/AX-2134-unified-release-mechanism branch from b2c677f to 7bcf5d8 Compare September 7, 2026 07:48
@YoniMelki
YoniMelki merged commit e4aed6a into main Sep 7, 2026
3 checks passed
@YoniMelki
YoniMelki deleted the feature/AX-2134-unified-release-mechanism branch September 7, 2026 10:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants